Tracking cloud installation information using cloud-aware kernel of operating system

ABSTRACT

Embodiments relate to systems and methods for tracking cloud installation information using a cloud-aware kernel of operating system. A guest operating system can be hosted in a cloud-based network which to support a set of virtual machines operating in that set of host clouds. The guest operating system can be configured with resources in the kernel to detect and manage the identity of the cloud in which the operating system is installed, as well as the duration of operation of the operating system and potentially, usage and other details of the set of virtual machines and their associated guest operating systems. Because the cloud identification and other data capture occurs directly in a cloud-aware kernel of the guest operating system, security and responsiveness are enhanced. The resulting set of kernel hosting data can be securely exported to a metering system or other platform for billing or other purposes.

FIELD

The invention relates generally to systems and methods for trackingcloud installation information using a cloud-aware kernel of operatingsystem, and more particularly, to platforms and techniques for acloud-aware kernel of an operating system that can be installed in oneor more host clouds to operate virtual machines and other entities, andwhich kernel can automatically detect the identity and type of cloud inwhich it is installed, as well as the duration of its operation in thehost cloud or clouds.

BACKGROUND

The advent of cloud-based computing architectures has opened newpossibilities for the rapid and scalable deployment of virtual Webstores, media outlets, social networking sites, and many other on-linesites or services. In general, a cloud-based architecture deploys a setof hosted resources such as processors, operating systems, software andother components that can be combined together to form virtual machines.A user or customer can request the instantiation of a virtual machine orset of machines from those resources from a central server or cloudmanagement system to perform intended tasks, services, or applications.For example, a user may wish to set up and instantiate a virtual serverfrom the cloud to create a storefront to market products or services ona temporary basis, for instance, to sell tickets to or merchandise foran upcoming sports or musical performance. The user can subscribe to theset of resources needed to build and run the set of instantiated virtualmachines on a comparatively short-term basis, such as hours or days, fortheir intended application.

Typically, when a user utilizes a cloud, the user must track thesoftware applications executed in the cloud and/or processesinstantiated in the cloud. For example, the user must track the cloudprocesses to ensure that the correct cloud processes have beeninstantiated, that the cloud processes are functioning properly and/orefficiently, that the cloud is providing sufficient resources to thecloud processes, and so forth. Due in part to the user's requirementsand overall usage of the cloud, the user may have many applicationsand/or processes instantiated in a cloud at any given instant, and theuser's deployment of virtual machines, software, and other resources canchange dynamically over time. In cases, the user may also utilizemultiple independent host clouds to support the user's cloud deployment.That user may further instantiate and use multiple applications or othersoftware or services inside or across multiple of those cloudboundaries, and those resources may be used or consumed by multiple ordiffering end-user groups in those different cloud networks.

In terms of the installation of a guest operating system in a host cloudor clouds, based upon which operating system layer guest operatingsystems for virtual machines can be instantiated, in known cloudmanagement platforms and operating systems, the operating system itselfis not configured to detect the host cloud in which it is installed, norto maintain a record of how long the operating system has beenoperating. Due to the lack of operating system self-awareness,administrators wishing to configure the operating system for particularcloud resources or conditions, or to track the operation of the guestoperating system over time for billing or other purposes, may need toresort to installing third-party services or tools on top of the guestoperating system, or on the host operating system or hypervisor, inorder to acquire similar information. Third-party tools or services may,however, present security risks to sensitive operating system or usageinformation, and because they may operate above the kernel, may be ableto be switched off by users or others without the knowledge of theadministrator.

It may be desirable to provide systems and methods for tracking cloudinstallation information using a cloud-aware operating system kernel, inwhich a guest operating system for a cloud-based implementation can beconfigured with a kernel that has a native cloud-awareness capability toidentify the host cloud in which it is installed or operates, as well asto track the duration of operation of the operating system or any childprocess, and/or to capture other data directly in the kernel itself.This information can in turn be made available either directly to a“user” of the operating system, which could include third party servicesor agents, but which could also be broadcast for remote consumption byother cloud management systems.

DESCRIPTION OF DRAWINGS

FIG. 1 illustrates an overall cloud system architecture in which variousaspects of systems and methods for tracking cloud installationinformation using a cloud-aware kernel of operating system can beimplemented, according to embodiments;

FIG. 2 illustrates an overall cloud system architecture in which variousaspects of systems and methods for tracking cloud installationinformation using a cloud-aware kernel of operating system can beimplemented, in further regards;

FIG. 3 illustrates a network configuration in which systems and methodsfor tracking cloud installation information using a cloud-aware kernelof operating system can be implemented, including kernel-based cloudawareness capabilities;

FIG. 4 illustrates an exemplary hardware configuration for a cloudmanagement system and/or other hardware that can support and maintainone or more cloud-based networks, according to various embodiments; and

FIG. 5 illustrates a flowchart for the analysis and processing ofcloud-related information capture at the kernel level of a cloud-basedoperating system, according to various embodiments

DESCRIPTION

Embodiments described herein can be implemented in or supported by acloud network architecture. As used herein, a “cloud” can comprise acollection of hardware, software, services, and/or resources that can beinvoked to instantiate a virtual machine, process, or other resource fora limited or defined duration. As shown for example in FIG. 1, thecollection of resources supporting a cloud 102 can at a hardware levelcomprise a set of resource servers 108 configured to deliver computingcomponents needed to instantiate a virtual machine, process, service, orother resource. For example, one group of resource servers in set ofresource servers 108 can host and serve an operating system, and/orcomponents, utilities, or interfaces related to that operating system,to deliver to a virtual target, and instantiate that machine with animage of that operating system. Another group of servers in set ofresource servers 108 can accept requests to host computing cycles orprocessor time, memory allocations, communications ports or links,and/or other resources to supply a defined level of processing power orthroughput for a virtual machine. A further group of resource servers inset of resource servers 108 can host and serve applications or othersoftware to load on an instantiation of a virtual machine, such as anemail client, a browser application, a messaging application, or otherapplications, software, or services. Other types of resource servers canbe used to support one or more clouds 102.

In embodiments, the entire set of resource servers 108 and/or otherhardware or software resources used to support one or more clouds 102,along with the set of instantiated virtual machines, can be managed by acloud management system 104. The cloud management system 104 cancomprise a dedicated or centralized server and/or other software,hardware, services, and network tools that communicate via network 106,such as the Internet or other public or private network, with allservers in set of resource servers 108 to manage the cloud 102 and itsoperation. To instantiate a new or updated set of virtual machines, auser can transmit an instantiation request to the cloud managementsystem 104 for the particular type of virtual machine they wish toinvoke for their intended application. A user can for instance make arequest to instantiate a set of virtual machines configured for email,messaging or other applications from the cloud 102. The virtual machinescan be instantiated as virtual client machines, virtual appliancemachines consisting of special-purpose or dedicated-task machines asunderstood in the art, and/or as other virtual machines or entities. Therequest to invoke and instantiate the desired complement of virtualmachines can be received and processed by the cloud management system104, which identifies the type of virtual machine, process, or otherresource being requested in that platform's associated cloud. The cloudmanagement system 104 can then identify the collection of hardware,software, service, and/or other resources necessary to instantiate thatcomplement of virtual machines or other resources. In embodiments, theset of instantiated virtual machines or other resources can, forexample, and as noted, comprise virtual transaction servers used tosupport Web storefronts, Web pages, and/or other transaction sites.

In embodiments, the user's instantiation request can specify a varietyof parameters defining the operation of the set of virtual machines tobe invoked. The instantiation request, for example, can specify adefined period of time for which the instantiated collection ofmachines, services, or processes is needed. The period of time can be,for example, an hour, a day, a month, or other interval of time. Inembodiments, the user's instantiation request can specify theinstantiation of a set of virtual machines or processes on a task basis,rather than for a predetermined amount or interval of time. Forinstance, a user could request a set of virtual provisioning servers andother resources until a target software update is completed on apopulation of corporate or other machines. The user's instantiationrequest can in further regards specify other parameters that define theconfiguration and operation of the set of virtual machines or otherinstantiated resources. For example, the request can specify a specificminimum or maximum amount of processing power or input/output (I/O)throughput that the user wishes to be available to each instance of thevirtual machine or other resource. In embodiments, the requesting usercan for instance specify a service level agreement (SLA) acceptable fortheir desired set of applications or services. Other parameters andsettings can be used to instantiate and operate a set of virtualmachines, software, and other resources in the host clouds. One skilledin the art will realize that the user's request can likewise includecombinations of the foregoing exemplary parameters, and others. It maybe noted that “user” herein can include a network-level user orsubscriber to cloud-based networks, such as a corporation, governmententity, educational institution, and/or other entity, includingindividual users and groups of users.

When the request to instantiate a set of virtual machines or otherresources has been received and the necessary resources to build thosemachines or resources have been identified, the cloud management system104 can communicate with one or more set of resource servers 108 tolocate resources to supply the required components. Generally, the cloudmanagement system 104 can select servers from the diverse set ofresource servers 108 to assemble the various components needed to buildthe requested set of virtual machines, services, or other resources. Itmay be noted that in some embodiments, permanent storage, such asoptical storage or hard disk arrays, may or may not be included orlocated within the set of resource servers 108 available to the cloudmanagement system 104, since the set of instantiated virtual machines orother resources may be intended to operate on a purely transient ortemporary basis. In embodiments, other hardware, software or otherresources not strictly located or hosted in one or more clouds 102 canbe accessed and leveraged as needed. For example, other software orservices that are provided outside of one or more clouds 102 acting ashosts, and are instead hosted by third parties outside the boundaries ofthose clouds, can be invoked by in-cloud virtual machines or users. Forfurther example, other non-cloud hardware and/or storage services can beutilized as an extension to the one or more clouds 102 acting as hostsor native clouds, for instance, on an on-demand, subscribed, orevent-triggered basis.

With the resource requirements identified for building a network ofvirtual machines, the cloud management system 104 can extract and buildthe set of virtual machines or other resources on a dynamic, on-demandbasis. For example, one set of resource servers 108 may respond to aninstantiation request for a given quantity of processor cycles with anoffer to deliver that computational power immediately and guaranteed forthe next hour or day. A further set of resource servers 108 can offer toimmediately supply communication bandwidth, for example on a guaranteedminimum or best-efforts basis, for instance over a defined window oftime. In other embodiments, the set of virtual machines or otherresources can be built on a batch basis, or at a particular future time.For example, a set of resource servers 108 may respond to a request forinstantiation of virtual machines at a programmed time with an offer todeliver the specified quantity of processor cycles within a specificamount of time, such as the next 12 hours. Other timing and resourceconfigurations are possible.

After interrogating and receiving resource commitments from the set ofresource servers 108, the cloud management system 104 can select a groupof servers in the set of resource servers 108 that match or best matchthe instantiation request for each component needed to build the user'srequested virtual machine, service, or other resource. The cloudmanagement system 104 for the one or more clouds 102 acting as thedestination for the virtual machines can then coordinate the integrationof the identified group of servers from the set of resource servers 108,to build and launch the requested set of virtual machines or otherresources. The cloud management system 104 can track the identifiedgroup of servers selected from the set of resource servers 108, or otherdistributed resources that are dynamically or temporarily combined, toproduce and manage the requested virtual machine population, services,or other cloud-based resources.

In embodiments, the cloud management system 104 can generate a resourceaggregation table or other record that identifies the various selectedsets of resource servers in set of resource servers 108 that will beused to supply the components of the set of instantiated virtualmachines, services, or processes. The selected sets of resource serverscan be identified by unique identifiers such as, for instance, Internetprotocol (IP) addresses or other addresses. In aspects, different setsof servers in set of resource servers 108 can be selected to deliverdifferent resources to different users and/or for differentapplications. The cloud management system 104 can register the finalizedgroup of servers in the set resource servers 108 contributing to orotherwise supporting the set of instantiated machines, services, orprocesses.

The cloud management system 104 can then set up and launch theinitiation process to instantiate the virtual machines, processes,services, and/or other resources to be hosted and delivered from the oneor more clouds 102. The cloud management system 104 can for instancetransmit an instantiation command or instruction to the registered groupof servers in the set of resource servers 108. The cloud managementsystem 104 can receive a confirmation message back from each registeredserver in set of resource servers 108 indicating a status or stateregarding the provisioning of their respective resources. Variousregistered resource servers may confirm, for example, the availabilityof a dedicated amount of processor cycles, amounts of electronic memory,communications bandwidth, services, and/or applications or othersoftware prepared to be served and delivered.

As shown for example in FIG. 2, after coordination of the sources andconfiguration of resources including the hardware layer, selectedsoftware, and/or other resources, the cloud management system 104 canthen instantiate a set of virtual machines 116, and/or other appliances,services, processes, and/or entities, based on the resources supplied byservers within set of resource servers 108 registered to support the oneor more clouds 102 in a multiple-cloud network 110. According toaspects, cloud management system 104 can access or interact with avirtualization module, platform, or service to instantiate and operateset of virtual machines 116, such as the kernel-based virtualizationmanager (KVM™) available from Red Hat, Inc. of Raleigh, N.C., or others.In embodiments, the cloud management system 104 can instantiate a givennumber, for example, 10, 500, 1000, 20,000, or other numbers orinstances of virtual machines to populate one or more clouds 102 and bemade available to users of that cloud or clouds. In aspects, users mayaccess the one or more clouds 102 via the Internet, or other public orprivate networks. Each virtual machine can be assigned an instantiatedmachine ID that can be stored in the resource aggregation table, orother record or image of the instantiated virtual machine population.Additionally, the cloud management system 104 can store data related tothe duration of the existence or operation of each operating virtualmachine, as well as the collection of resources utilized by the overallset of instantiated virtual machines 116.

In embodiments, the cloud management system 104 can further store, trackand manage each user's identity and associated set of rights orentitlements to software, hardware, and other resources. Each user thatoperates a virtual machine or service in the set of virtual machines inthe cloud can have specific rights and resources assigned and madeavailable to them, with associated access rights and securityprovisions. The cloud management system 104 can track and configurespecific actions that each user can perform, such as the ability toprovision a set of virtual machines with software applications or otherresources, configure a set of virtual machines to desiredspecifications, submit jobs to the set of virtual machines or otherhost, manage other users of the set of instantiated virtual machines 116or other resources, and/or other privileges, entitlements, or actions.The cloud management system 104 associated with the virtual machine(s)of each user can further generate records of the usage of instantiatedvirtual machines to permit tracking, billing, and auditing of theresources and services consumed by the user or set of users. In aspectsof the present teachings, the tracking of usage activity for one or moreuser (including network level user and/or end-user) can be abstractedfrom any one cloud to which that user is registered, and made availablefrom an external or independent usage tracking service capable oftracking software and other usage across an arbitrary collection ofclouds, as described herein. In embodiments, the cloud management system104 of an associated cloud can for example meter the usage and/orduration of the set of instantiated virtual machines 116, to generatesubscription and/or billing records for a user that has launched thosemachines. In aspects, tracking records can in addition or instead begenerated by an internal service operating within a given cloud. Othersubscription, billing, entitlement and/or value arrangements arepossible.

The cloud management system 104 can configure each virtual machine inset of instantiated virtual machines 116 to be made available to usersvia one or more networks 116, such as the Internet or other public orprivate networks. Those users can for instance access set ofinstantiated virtual machines via a browser interface, via anapplication server such as a Java™ server, via an applicationprogramming interface (API), and/or other interface or mechanism. Eachinstantiated virtual machine in set of instantiated virtual machines 116can likewise communicate with its associated cloud management system 104and the registered servers in set of resource servers 108 via a standardWeb application programming interface (API), or via other calls,protocols, and/or interfaces. The set of instantiated virtual machines116 can likewise communicate with each other, as well as other sites,servers, locations, and resources available via the Internet or otherpublic or private networks, whether within a given cloud in one or moreclouds 102, or between those or other clouds.

It may be noted that while a browser interface or other front-end can beused to view and operate the set of instantiated virtual machines 116from a client or terminal, the processing, memory, communications,storage, and other hardware as well as software resources required to becombined to build the virtual machines or other resources are all hostedremotely in the one or more clouds 102. In embodiments, the set ofvirtual machines 116 or other services, machines, or resources may notdepend in any degree on or require the user's own on-premise hardware orother resources. In embodiments, a user can therefore request andinstantiate a set of virtual machines or other resources on a purelyoff-premise basis, for instance to build and launch a virtualstorefront, messaging site, and/or any other application. Likewise, oneor more clouds 102 can also be formed in whole or part from resourceshosted or maintained by the users of those clouds, themselves.

Because the cloud management system 104 in one regard specifies, builds,operates and manages the set of instantiated virtual machines 116 on alogical or virtual level, the user can request and receive differentsets of virtual machines and other resources on a real-time or nearreal-time basis, without a need to specify, install, or configure anyparticular hardware. The user's set of instantiated virtual machines116, processes, services, and/or other resources can in one regardtherefore be scaled up or down immediately or virtually immediately onan on-demand basis, if desired. In embodiments, the set of resourceservers 108 that are accessed by the cloud management system 104 tosupport the set of instantiated virtual machines 116 or processes canchange or be substituted, over time. The type and operatingcharacteristics of the set of instantiated virtual machines 116 cannevertheless remain constant or virtually constant, since instances areassembled from a collection of abstracted resources that can be selectedand maintained from diverse sources based on uniform specifications.Conversely, the users of the set of instantiated virtual machines 116can also change or update the resource or operational specifications ofthose machines at any time. The cloud management system 104 and/or otherlogic can then adapt the allocated resources for that population ofvirtual machines or other entities, on a dynamic basis.

In terms of network management of the set of instantiated virtualmachines 116 that have been successfully configured and instantiated,the one or more cloud management systems 104 associated with thosemachines can perform various network management tasks includingsecurity, maintenance, and metering for billing or subscriptionpurposes. The cloud management system 104 of one or more clouds 102 can,for example, install, initiate, suspend, or terminate instances ofapplications or appliances on individual machines. The cloud managementsystem 104 can similarly monitor one or more operating virtual machinesto detect any virus or other rogue process on individual machines, andfor instance terminate an application identified as infected, or avirtual machine detected to have entered a fault state. The cloudmanagement system 104 can likewise manage the set of instantiatedvirtual machines 116 or other resources on a network-wide or othercollective basis, for instance, to push the delivery a software upgradeto all active virtual machines or subsets of machines. Other networkmanagement processes can be carried out by cloud management system 104and/or other associated logic.

In embodiments, more than one set of virtual machines can beinstantiated in a given cloud at the same time, at overlapping times,and/or at successive times or intervals.

The cloud management system 104 can, in such implementations, build,launch and manage multiple sets of virtual machines as part of the setof instantiated virtual machines 116 based on the same or differentunderlying set of resource servers 108, with populations of differentvirtual machines such as may be requested by the same or differentusers. The cloud management system 104 can institute and enforcesecurity protocols in one or more clouds 102 hosting one or more sets ofvirtual machines. Each of the individual sets or subsets of virtualmachines in the set of instantiated virtual machines 116 can be hostedin a respective partition or sub-cloud of the resources of the maincloud 102. The cloud management system 104 of one or more clouds 102 canfor example deploy services specific to isolated or defined sub-clouds,or isolate individual workloads/processes within the cloud to a specificsub-cloud or other sub-domain or partition of the one or more clouds 102acting as host. The subdivision of one or more clouds 102 into distincttransient sub-clouds, sub-components, or other subsets which haveassured security and isolation features can assist in establishing amultiple user or multi-tenant cloud arrangement. In a multiple-userscenario, each of the multiple users can use the cloud platform as acommon utility while retaining the assurance that their information issecure from other users of the same one or more clouds 102. In furtherembodiments, sub-clouds can nevertheless be configured to shareresources, if desired.

In embodiments, and as also shown in FIG. 2, the set of instantiatedvirtual machines 116 generated in a first cloud in one or more clouds102 can also interact with a set of instantiated virtual machines,services, and/or processes generated in a second, third or further cloudin one or more clouds 102, comprising a multiple-cloud network 110. Thecloud management system 104 of a first cloud of one or more clouds 102can interface with the cloud management system 104 of a second, third,or further cloud of one or more clouds 102 to coordinate those domainsand operate the clouds and/or virtual machines, services, and/orprocesses on a combined basis. The cloud management system 104 of agiven cloud on one or more clouds 102 can in aspects track and manageindividual virtual machines or other resources instantiated in thatcloud, as well as the set of instantiated virtual machines or otherresources in other clouds.

In the foregoing and other embodiments, the user making an instantiationrequest or otherwise accessing or utilizing the cloud network can be aperson, customer, subscriber, administrator, corporation, organization,government, and/or other entity. In embodiments, the user can be orinclude another virtual machine, application, service and/or process. Infurther embodiments, multiple users or entities can share the use of aset of virtual machines or other resources.

Aspects of the present teachings relate to platforms and techniques inwhich the kernel of a guest operating system installed and operating ina host cloud-based network can be equipped or configured with a set ofcloud-awareness resources or capabilities. The cloud-aware operatingsystem kernel can be configured to contain capabilities and/or servicesto be able to detect and identify the identity, type, or otherinformation of the cloud in which the guest operating system isinstalled, directly at the kernel level and without a need to invokethird-party applications or services located outside of the kernel. Theguest operating system can thereby establish the identity of the cloudin which it is installed, and for instance automatically configure oradjust operating parameters, services, application programminginterfaces, and/or other resources to match the cloud host environmentin which it finds itself located. In aspects, the kernel and associatedtools can track the duration or length of time that the guest operatingsystem has been operating in the identified cloud, to export thatinformation to external consumers such as third-party billing ormetering applications, or others.

Consistent with the foregoing, in general, FIG. 3 shows an illustrativenetwork configuration in which systems and methods for tracking cloudinstallation information using a cloud-aware operating system kernel canbe implemented, according to various embodiments. In embodiments asshown, one or more users can operate a set of virtual machines 228 in aset of host clouds 142, for instance, by subscribing to resources in theset of host clouds 142 to support, provide, and/or execute the set ofvirtual machines 228 according to service level agreements (SLAs) and/orother terms or arrangements. In aspects, each virtual machine in the setof virtual machines 228 can have a set of applications 240 installed orinstantiated in that machine, such as browsing, messaging, wordprocessing, spreadsheet, and/or other applications or application types.According to aspects, each virtual machine in the set of virtualmachines 228 can operate using an instance of a guest operating system272 assigned to or supporting that machine in the associated cloud-basednetwork in the set of host clouds 142. Each host cloud in the set ofhost clouds 142 can be supported, hosted, and/or executed in or by acloud management system 104 associated with the set of host clouds 142.In aspects, the guest operating system 272 instantiated in one or moreclouds in the set of host clouds can be or include, for instance, theRed Hat Enterprise Linux™ operating system available from Red Hat, Inc.,Raleigh, N.C., or other operating systems or platforms. In aspects, theeach instance of the guest operating system 272 can serve or function tosupport the operation of an associated virtual machine set of virtualmachines 228 operating in the set of host clouds 142.

In aspects as shown, the kernel 270 of the guest operating system 272can be configured or equipped with a set of services or resourcesincluding a set of kernel services 232 to support task scheduling, filesupport, and other operating system services for an associated virtualmachine and/or other entities, as well as a cloud awareness engine 260configured to perform discovery and tracking operations in the cloudenvironment in which the guest operating system 272 is installed. Thecloud awareness engine 260 and/or other logic, application, platform,and/or service can be configured to build, access, update, and/ormaintain a kernel hosting record 262 to directly capture and storeinformation related to the location, duration, operation, and/or otherdetails related to the use and activity of guest operating system 272 inone or more host clouds in the set of host clouds 142. The kernelhosting record 262 can be configured to store a set of kernel hostingdata 264, including for instance cloud location information, operatingsystem duration information reflecting the period or length of time overwhich the guest operating system 272 and/or associated virtual machinesor applications have been executing and/or in use, public cloudregistration information, private cloud registration information, and/orother data related to the operation of guest operating system 272 in theset of host clouds 142 or otherwise. In aspects as shown, the cloudawareness engine 260 can be integrated, hosted, and/or embedded directlyin the kernel 270 of the guest operating system 272 itself, without arequirement for additional layers of software to perform cloudidentification and operating system management tasks.

In terms of identifying the actual cloud or clouds in the set of hostclouds 142 in which the guest operating system 272 is installed oroperates, the cloud awareness engine 260 and/or other logic,application, platform, and/or service can be configured to communicatewith one or more clouds in the set of host clouds 142 to interrogatethose clouds for a respective cloud identifier 266. The cloud identifier266 can be an identifier or code stored in or associated with each cloudin the set of host clouds 142 and/or other clouds, to identify thevendor, type, software compatibilities, subscription terms, resourcecapacities, and/or other data related to the cloud network environmentsupplied or offered by each cloud. In aspects, the cloud identifier 266can represent a unique identifier or code assigned to all public cloudsor other types of clouds, for instance, through a public registrymaintained by one or more cloud vendors and/or other organizations.According to aspects, the cloud awareness engine 260 and/or other logic,application, platform, and/or service can request, interrogate, access,and/or otherwise acquire the cloud identifier 266 for the cloud in whichit is installed, for instance by querying the cloud management system104 associated with that cloud, and/or interrogating other entities,platforms, sources, and/or services. In implementations, the cloudawareness engine 260 and/or other logic, application, platform, and/orservice can communicate with the cloud management system 104 and/orother entities via secure channels and/or private channels, such asencrypted channels or other connections.

In aspects, the cloud awareness engine 260 and/or other logic,application, platform, and/or service can likewise request or acquireother data directly or internally from the host cloud or cloud(s) inwhich it is installed or operates, including duration information aspart of the set of kernel hosting data 264. The duration information canreflect the length, amount, and/or period of time over which the guestoperating system 272, set of applications 240, set of virtual machines228, and/or other operating systems, machines, and/or other entitieshave been installed, instantiated, and/or otherwise operating in the setof host clouds 142 using the guest operating system 272. The durationinformation can be stored by the cloud management system 104 and/orother logic or service associated with the host cloud or clouds in theset of host clouds 142 in which guest operating system 272 is installedand/or operates.

In aspects, the duration information can be associated with and/or usedfor purposes of metering and billing the end-user of one or more of theset of virtual machines 228 or other users, based on time of operatingsystem use, resource consumption data, and/or other variables. Inaspects, the cloud awareness engine 260 and/or other logic, application,platform, and/or service can be configured to access the kernel hostingrecord 262 and transmit duration information as well as other data inthe set of kernel hosting data 264 to an external, third-party, and/orother metering system 270 for receipt and consumption by that system. Inaspects, the metering system 270 can be configured to accesssubscription information for the subject user via subscription databasesor other sources, to generate or process billing records or othersubscription events or activities, based on the duration of operation ofthe guest operating system 272, set of virtual machines 228, set ofapplications 240, and/or other uses or factors. In aspects, the cloudawareness engine 260 and/or other logic, application, platform, and/orservice can communicate with an entitlement engine 140 (FIG. 4)configured to record and administer subscription information for the setof host clouds, with that engine for instance installed in the cloudmanagement system 104 and/or other host or location. The cloud awarenessengine 260 can also be connected to metering system 270 via a securechannel or connection, if desired. The same or similar duration,subscription, and/or metering information can also be shared or storedto the cloud management system 104 of the corresponding host cloud,and/or to other locations.

FIG. 4 illustrates an exemplary diagram of hardware and other resourcesthat can be incorporated in a cloud management system 104 configured tocommunicate with the set of instantiated virtual machines 116, cloudawareness engine 260, entitlement engine 140, set of host clouds 142,and/or other entities, services, or resources via one or more networks106 and/or other connections, according to embodiments. In embodimentsas shown, the cloud management system 104 can comprise a processor 130communicating with memory 132, such as electronic random access memory,operating under control of or in conjunction with an operating system136. The operating system 136 can be, for example, a distribution of theLinux™ operating system, the Unix™ operating system, or otheropen-source or proprietary operating system or platform. The processor130 also communicates with a cloud store 138, such as a database storedon a local hard drive, a management engine 128, an entitlement engine140, and the cloud awareness engine 260 to execute control logic andcontrol the operation of the set of virtual machines 228 and/or otherresources in the set of host clouds 142, and/or other collections ofclouds. The processor 130 further communicates with a network interface134, such as an Ethernet or wireless data connection, which in turncommunicates with the one or more networks 106, such as the Internet orother public or private networks. The processor 130 and/or the cloudmanagement system 104 can likewise communicate with other interfaces,applications, machines, sites, services, data, and/or logic. Otherconfigurations of the cloud management system 104, associated networkconnections, and other hardware, software, and service resources arepossible. It may be noted that in embodiments, other hardware machines,platforms, or engines can comprise the same or similar resources ascloud management system 104, or can be configured with differenthardware and software resources.

FIG. 5 illustrates a flowchart of overall processing to perform variouscloud-identification and other operations using kernel-based operatingsystem resources, according to various embodiments of the presentteachings. In 502, processing can begin. In 504, the guest operatingsystem 272 can be installed or associated with one or more clouds in theset of host clouds 142, to support the operation of the set of virtualmachines 228 operating or to be operated in that cloud or clouds.

In 506, the cloud identifier 266 for the cloud or clouds in which guestoperating system 272 is installed or operating can be acquired in thecloud awareness engine 260 and/or other logic, application, platform,and/or service hosted in the kernel 270 of the guest operating system272. In 508, the cloud awareness engine 260 and/or other logic,application, platform, and/or service can identify the guest operatingsystem 272 as being installed or registered in a public cloud and/or aprivate cloud, as appropriate. In 510, the cloud awareness engine 260and/or other logic, application, platform, and/or service can accessand/or initiate the kernel hosting record 262 in the kernel 270 of theguest operating system 272, including the set of kernel hosting data264.

In 512, the set of virtual machines 228 scan be installed and/orinstantiated in the set of host clouds 142. In 514, the cloud awarenessengine 260 and/or other logic, application, platform, and/or service canrecord, capture, and/or update the set of kernel hosting data 264related to operation of the guest operating system 272, and/or relatedinformation, in the kernel hosting record 262. In aspects, the kernelhosting data 264 can including operations related to the support of theset of virtual machines 228, the set of applications 140, and/or otherinformation or data.

In 516, the cloud awareness engine 260 and/or other logic, application,platform, and/or service can export or transmit the kernel hostingrecord 262 to a metering system 270, such as an external and/or othermetering, billing, or administrative platform or service. In aspects,the kernel hosting record 262 can also or instead be transmitted toother applications or services, including potential third-party,internal, and/or external applications, services, and/or platforms foradministrative, billing, or other purposes. In 518, cloud operations inthe set of host clouds 142 can continue using the guest operating system272, with updates to the kernel hosting record 262 accordingly beingmade, as appropriate. in 520, as understood by persons skilled in theart, processing can repeat, return to a prior processing point, jump toa further processing point, or end.

The foregoing description is illustrative, and variations inconfiguration and implementation may occur to persons skilled in theart. For example, while embodiments have been described in which thecloud management system 104 for a particular cloud resides in a singleserver or platform, in embodiments the cloud management system 104 andassociated logic can be distributed among multiple servers, services, orsystems. Similarly, while embodiments have been described in which onegroup of servers within a set of resource servers 108 can provide onecomponent to build a requested set of virtual machines, in embodiments,one group of resource servers can deliver multiple components topopulate the requested set of instantiated virtual machines 116, and/orother machines, entities, services, or resources. Other resourcesdescribed as singular or integrated can in embodiments be plural ordistributed, and resources described as multiple or distributed can inembodiments be combined. The scope of the invention is accordinglyintended to be limited only by the following claims.

What is claimed is:
 1. A method comprising: querying, by a kernel of aguest operating system, for a cloud identifier to identify a host cloudin which the guest operating system is installed, wherein the host cloudcomprises a plurality of physical computer clusters that are accessibleover a network to deliver computational resources, wherein the guestoperating system operates on a machine of a first physical computercluster of the plurality of physical computer clusters in the hostcloud; responsive to querying for the cloud identifier to identify thehost cloud in which the guest operating system is installed, receiving,by the kernel, the cloud identifier that identifies the host cloud inwhich the guest operating system is installed; determining, by thekernel, duration information indicative of a length of time the guestoperating system operates in the host cloud; and storing, by the kernel,the cloud identifier and the duration information in a kernel hostingrecord of the kernel of the guest operating system, wherein the storingis performed at a kernel-space level rather than at a user space level.2. The method of claim 1, further comprising instantiating a set ofvirtual machines each hosted by an instance of the guest operatingsystem.
 3. The method of claim 2, further comprising storing a usagehistory of the set of virtual machines and the guest operating system.4. The method of claim 3, further comprising storing data related to theusage history in an exportable kernel hosting record.
 5. The method ofclaim 1, further comprising exporting the kernel hosting record to anexternal metering system.
 6. The method of claim 5, wherein the externalmetering system is to generate a subscription billing event in view ofthe kernel hosting record.
 7. The method of claim 1, further comprisingacquiring an updated cloud identifier in view of a change in the hostcloud.
 8. The method of claim 1, wherein the host cloud comprises aplurality of host clouds.
 9. The method of claim 1, wherein the kernelhosting record comprises an identification of a public class or aprivate class for the host cloud.
 10. The method of claim 1, wherein thecloud identifier comprises a unique publicly registered identificationcode.
 11. A system comprising: a memory; and a processor,communicatively coupled to the memory, to: query, by a kernel of a guestoperating system, for a cloud identifier to identify a host cloud inwhich the guest operating system is installed, wherein the host cloudcomprises a plurality of physical computer clusters that are accessibleover a network to deliver computational resources, wherein the guestoperating system operates on a machine of a first physical computercluster of the plurality of physical computer clusters in the hostcloud; receive, by the kernel, in response to the query for the cloudidentifier to identify the host cloud in which the guest operatingsystem is installed, the cloud identifier that identifies the host cloudin which the guest operating system is installed; determine, by thekernel, duration information indicative of a length of time the guestoperating system operates in the host cloud; and store, by the kernel,the cloud identifier and the duration information in a kernel hostingrecord at the kernel of the guest operating system, wherein the storingis performed at a kernel-space level rather than at a user space level.12. The system of claim 11, wherein the processor is further toinstantiate a set of virtual machines each hosted by an instance of theguest operating system.
 13. The system of claim 12, wherein theprocessor is further to store a usage history of the set of virtualmachines and the guest operating system.
 14. The system of claim 13,wherein the processor is further to store data related to the usagehistory in an exportable kernel hosting record.
 15. The system of claim11, wherein the processor is further to export the kernel hosting recordto an external metering system to generate a subscription billing eventin view of the kernel hosting record.
 16. The system of claim 11,wherein the processor is further to acquire an updated cloud identifierin view of a change in the host cloud.
 17. The system of claim 11,wherein the kernel hosting record comprises an identification of apublic class or a private class for the host cloud.
 18. The system ofclaim 11, wherein the cloud identifier comprises a unique publiclyregistered identification code.
 19. A non-transitory computer-readablemedium comprising instructions that, responsive to execution by aprocessing device, cause the processing device to perform operationscomprising: querying, by a kernel of a guest operating system, for acloud identifier to identify a host cloud in which the guest operatingsystem is installed, wherein the host cloud comprises a plurality ofphysical computer clusters that are accessible over a network to delivercomputational resources, wherein the guest operating system operates ona machine of a first physical computer cluster of the plurality ofphysical computer clusters in the host cloud; responsive to querying forthe cloud identifier to identify the host cloud in which the guestoperating system is installed, receiving, by the kernel, the cloudidentifier that identifies the host cloud in which the guest operatingsystem is installed; determining, by the kernel, duration informationindicative of a length of time the guest operating system operates inthe host cloud; and storing, by the kernel, the cloud identifier and theduration information in a kernel hosting record of the kernel of theguest operating system, wherein the storing is performed at akernel-space level rather than at a user space level.
 20. Thenon-transitory computer-readable medium of claim 19, wherein the kernelhosting record comprises an identification of a public class or aprivate class for the host cloud.